Docs: sync upstream clickhouse-operator docs updates#80
Closed
mintlify[bot] wants to merge 1 commit into
Closed
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Syncs documentation updates from
clickhouse/clickhouse-operatorintoproducts/kubernetes-operator/to reflect the newadditionalPortsClickHouseCluster CRD field.cc @GrigoryPervakov for review (author of upstream clickhouse-operator#197).
Changes
products/kubernetes-operator/reference/api-reference.mdx— adds the newAdditionalPorttype section and theadditionalPortsrow inClickHouseClusterSpec, copied verbatim from upstream commit7e82242("feat: allow exposing additional ports on ClickHouse service and pods", #197).products/kubernetes-operator/install/olm.mdx— trailing newline alignment with upstream.Context
Upstream source commit:
7e82242af1ef32ec951ad5c6c88ff64b0e5299eb(PR #197).Conflicts / issues
guides/configuration.mdxandguides/introduction.mdx(/concepts/...→/core/concepts/...,/reference/...→/core/reference/...) were intentionally not overwritten — these are downstream-only path adjustments for this Mintlify site. No upstream content changes touched these files, so there is no real conflict; flagging only for visibility.README.md,development.md,styles/,templates/) are not synced — they are not part of the published Mintlify docs.mint validatepasses.mint broken-linksreports 2 unrelated pre-existing broken links inintegrations/language-clients/java/jdbc.mdx(not caused by this sync).Note
Low Risk
Documentation-only sync with no runtime, auth, or data-path changes.
Overview
Syncs clickhouse-operator upstream docs into
products/kubernetes-operator/so the published API reference matches the newadditionalPortsCRD capability.The
api-reference.mdxpage gains anAdditionalPortsection (name,port) and documentsClickHouseClusterSpec.additionalPorts: extra TCP ports on ClickHouse pods and the operator headless Service, with a note that Kubernetes exposure does not by itself make ClickHouse listen on those ports.install/olm.mdxonly picks up a trailing newline from upstream.Reviewed by Cursor Bugbot for commit 28b7759. Bugbot is set up for automated code reviews on this repo. Configure here.